home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d20
/
tick207.arc
/
BETATICK.DOC
next >
Wrap
Text File
|
1991-02-08
|
13KB
|
291 lines
Betatic.doc
Tick 2.01 -
* Fixed the INTL line in MSG attaches so that it terminates
with a CR/LF rather than with just a LF.
* Fixed a bad error message which occurred when you had an
invalid zone.
Tick 2.02 -
* Fixed a couple of spots where an error would be be
properly handled, but not logged.
* TICK now has PASSTHRU capability! To make an area a
passthru area, place a "LOCAL PASSTHRU" entry in its AREA block,
as you would other "LOCAL" keywords. That will activate addi-
tional processing. TICK will make its attaches as usual, but
will *not* update the FILES.BBS. At each run thereafter, TICK
will test all attaches (either MSG or FLO's, for FIDO or native
mode respectively), and will kill the file when there are no ac-
tive attaches. If the passthrough file is also a pre-release
file, the passthrough process will be postponed until the file is
released. Be aware that if you define a secondary area, and that
secondary area is passthru, the file will be tossed there and
treated as a passthru file (ie - deleted). Likewise, if a non-
passthru area is secondary to an area that *is* passthru, the in-
bounds will be tossed to the non-passthru area and treated as
non-passthru. (These actions will be infulenced by stopdup, as
previously). A note of caution ... This code is new, and there
could be some risk of inadvertant loss of files if there are bugs
in it. I have run preliminary tests, which appear to have gone
OK.
Tick 2.03 -
* I forgot to mention that the maximun number of nodes per
area has been increased to 100, as of 2.02.
* As per popular request, TICK now provides for "Terminal
Nodes". If a node has a "T" flag, it will receive the FILE, but
not the TIC.
* Fido mode MSG attaches will once again try to make *ONE*
MSG for both file and TIC, unless the file being processed is a
pre-release file.
1
Betatic.doc
Tick 2.04 -
* Tick users may now choose between the "#" flag and the
"^" flag in FLO files, to select the method of killing the TIC
files after they are sent. The default is to set the "#" flag,
which instructs the mailer to truncate the file after sending.
TICK will delete it on the following run. If you place the
keyword "MailerKills" in the CFG file, TICK will use the "^"
flag, and assumes that the mailer will kill the TIC file after it
is sent. NOTE: When you first make this conversion, any exist-
ing attaches of TICs will still be truncated rather than deleted.
You will need to either run a program that will kill the remain-
ing 0-length files in the HOLD directory (such as Kill0.LZH),
delete them manually, or do a run of TICK *without* the
MailerKills flag to get rid of those old ones.
* Tick will now try to *deactivate* a poorly defined AREA
instead of aborting the program. If a file for a deactivated
area comes in , TICK will act as if the area does not exist.
Please test this with such things as non-existant directories,
etc.
Tick 2.06 -
* There is a new configuration keyword for HATCH. If you
add the keyword "RAID" to your TIC.CFG, HATCH will generate a new
file in the HOLD directory. The file will have the extention
"RAD", and should enable a future version of RAID (and any other
file anouncement program that cares to use it) to announce files
that are locally hatched.
* TICK and HATCH are now being compiled with MSC 6.00A.
Watch for any strange behavior.
* TICK now supports a REPLACE function. If an inbound TIC
has a "Replaces abc.xyz" line in it, and if you configure TICK to
allow it, the old file (if it exists in the destination direc-
tory) will be either deleted or moved to a different directory
before the new file is moved to the destination. To activate
this feature, add the keyword "REPLACE" to your TIC.CFG. That
will cause the replace function to be active in all areas, and
will result in old versions being DELETED if the inbound TIC has
that name as the parameter of the REPLACES line. If you follow
the "REPLACE" keyword with a vaild directory name, the old file
will be moved there instead. If a file by the same name already
exists in the "old file" directory, TICK will leave the file
alone and note that in the log. The Replace function does not
accept wildcards for replacement ... I felt that the security
issues were too great. There are also 2 additional LOCAL
keywords ... If you have put a REPLACE line in your TIC.CFG, but
do NOT want to allow replacements in certaing areas, then add a
2
Betatic.doc
"LOCAL NoReplace" line in those AREA blocks (after the AREA line,
but before the node list). If you do NOT want REPLACE to be ac-
tive in most areas, but DO want it in certain areas, then do not
put a REPLACE line in your TIC.CFG, and add a "LOCAL REPLACE"
line to those AREA blocks. Note that if you want a replaced file
to be MOVED to an "old files" directory, you must put a REPLACE
line in the CFG. (ie - Local "Replace c:\oldfiles" is NOT
valid). I should mention that TICK will not remove the entry
from the FILES.BBS at this time. There are many permutations of
CFG's with this feature, please pound on it to shake loose any
bugs that might be lurking.
* HATCH now accepts an optional command line switch to allow
you to designate a filename to replace with the file you are now
hatching. The switch is /X, and must be immediately (no spaces)
followed by the filename you are replaceing. The filename should
NOT contain a path, Drive letter, or wildcard characters (* or
?). There is presently no interactive prompt for a "Replaces"
filename. (Should there be one?)
TICK 2.06b - (HATCH only)
* Corrects a bug in HATCH introduced in 2.06 ... If you en-
tered the filename from the command line, it was being truncated
to 13 characters. That was fine if you were using the default
directory and allowing HATCH to determine the directory, but if
you wanted to HATCH something from another directory, it was
failing.
* HATCH now will prompt for a "replacement file" name if
you don't provide it on the command line. To bypass the prompt
when running in a batch file, you can supply the "/X" without a
filename appended ... ie - "Hatch /ffoo.txt /xold.txt" results in
the file Foo.yxy being hatched, and replacing old.txt on the
receiving nodes; "Hatch /ffoo.txt /x" will hatch the same file
and not prompt for a replacement; and "Hatch /ffoo.txt" will
hatch the file and prompt you for a replacement file name.
TICK 2.06c -
* Tick was in some cases generating duplicate attaches to
the same node. When I re-compiled it with MSC 5.1 instead of MSC
6.00A, the problem seems to have gone away.
TICK 2.06d -
* This version fixes a bug where each TICK that processed a
file containing a RELEASE line added another "release" line to
the TIC.
3
Betatic.doc
* New implementation of the NoWait option and the /X com-
mand line option ... Originally, NoWait was not really foolproof
when it came to unattended operation of HATCH. It assumed that
the operator had made a batch file that insured that the required
items, such as /fFile.ext and /aAreaname were provided. If the
items provided were invalid, it would abort the hatch, so as not
to hang the batch. If you failed to provide a filename or area
altogether, it would still prompt you. This version now tries to
catch this type of error. If there is missing required informa-
tion, Hatch should now abort if the /ON flag is in the command
line, or if NoWait is in the CFG. Also ... If you have specified
Nowait (/on), There is never a prompt for a "replaces" file or
for a RELEASE date. (You should no longer need to put the /R0 in
the command line). If you put the /Xfile.ext in the command
line, then file.ext will be used as the REPLACE file. If you
omit /X, there will be no replace file, and if you put "/X" in
the command line, but provide no replacement filename there, the
"/X" will be ignored. If you run in the interactive mode
(without the "/on" or NoWait), then you will be prompted for a
replacement file unless you provide one on the command line.
TICK 2.07 -
* Adds the LOCAL STOPDUP feature mentioned in the echo.
For those of you who might have missed it, here's how it works:
First, You still need to have the main [STOPDUP c:\dupdir]
line in your TIC.CFG to activate STOPDUP processing in the first
place. The presence of a LOCAL STOPDUP in an area all by itself
will NOT turn on STOPDUP in that area.
If you do not put a [LOCAL STOPDUP dupfile] statement in
your area, then that area's dup file will use the area's tag with
a DUP extention as the filename for its dup file, as before. If
you *do* put in the new local line, then the "dupfile" name that
follows the "Local Stopdup" will be the root name for that dup
file. It will be appended with a DUP extention. For example:
AREA d:\file\long BRAVO
Local Stopdup Tango
1:266/12 password *C
1:13/13 wordpass C
The DUP file for the above area would be called Tango.DUP,
and would reside in the Dup directory specified in the regular
STOPDUP cfg line. Without the local line, the file would have
been called BRAVO.DUP.
What this does is gives you the option of merging certain
echos to use the same DUP file. This possibility should be used
with care. Just because *YOU* happen to carry both of the merged
4
Betatic.doc
echos, that doesn't always insure that all your downstream nodes
carry both echos. If a DUP entry generated from echo A stops the
same file from passing in echo B, you may be preventing nodes who
carry only B from getting it at all.
Barry Geller
609-482-8604
1:266/12
5